feat: self-hosted Telegram bridge for the SDK (Fixes #1426) - #1427

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Nice idea and a genuinely useful addition — a zero-dependency example showing how to drive an agent from Telegram fits well alongside the other SDK examples, and per-chat session/queueing logic in telegram-bot.ts is clean.

The main issue is robustness for something meant to run continuously: main()'s while (true) loop calls tg('getUpdates', ...) with no try/catch (lines ~58-60). tg() throws on any non-2xx/non-ok response or network error, and since main() at the bottom is invoked without a .catch(), any transient Telegram outage, rate limit, or DNS blip kills the whole bot silently (unhandled rejection). For a script whose entire pitch is 'run this and forget it,' that's the first thing that will bite a real user. At minimum wrap the getUpdates call in try/catch with a short backoff/retry, and add main().catch(...) with a non-zero exit or log.

Smaller things worth a look before this is portable:

• The default agent id codebuff/base@0.0.16 is version-pinned and will go stale; consider defaulting to the unversioned id or documenting that it needs updating.
• No handling for Telegram's 409 conflict (another poller running) or getUpdates timeout edge cases.
• Worth double-checking the event.type === 'text' / event.source shape against the current SDK event types — I can't verify from the diff alone that this matches the real handleEvent payload.

With the crash-on-network-error issue fixed this looks like a solid, mergeable example.

Addressed in 22b957c:

• getUpdates polling loop now retries with exponential backoff (0.5s up to 10s) on transient failures; 401 and 409 abort with a clear message instead of silently spinning.
• Added a top-level main().catch() so unhandled rejections log and exit non-zero.
• FREEBUFF_AGENT default switched to the unversioned 'codebuff/base'.
• Checked the event contract: handleEvent receives PrintModeEvent (common/src/types/print-mode.ts), so the event.type === 'text' / event.source handling matches the SDK types; no change needed there.
• 409 specifically is Telegram's "another getUpdates in flight" conflict, so it's fatal for this script (only one poller can win).